Add operation setup wizard to the landing page - #51

Adds a gh-aw-wizard-style wizard to the landing page, rendered directly after the dispatch diagram: pick an operation, pick a coding agent, copy a prompt that creates the control repository and runs the operation.

Changes

• docs/components/OpsWizard.astro (new) — three-step wizard:
  1. Operation — options are read at build time from each package directory's aw.yml (name + description), so the list tracks the catalog instead of a hard-coded copy. A Custom operation option takes a free-form description and routes the prompt through the packaged create-ops-package skill.
  2. Coding agent — Copilot CLI, Claude Code, or Codex CLI, plus optional owner and control repository name. The selection drives the install/launch hint and the engine: value in the prompt.
  3. Prompt — live-rendered prompt with a clipboard copy button, plus a noscript fallback pointing at the Quickstart.
• docs/components/HierarchyHero.astro — renders <OpsWizard /> after the diagram figure. The hero override is only used by the splash landing page, and docs/README.md is plain Markdown, so this avoids pulling in MDX.

The generated prompt encodes the repository's safety defaults — private control plane, staged first run, package rollout variables capped at one repository, no hand-edits to .lock.yml:

4. Install the operation package: `gh aw add githubnext/central-agentic-ops/dependabot@main`.
...
- `gh variable set CENTRAL_AGENTIC_OPS_DEPENDABOT_MODE --body "staged"`
- Trigger one manual run: `gh workflow run dependabot.lock.yml --raw-field target_repo="acme/<target-repo>" ...`

Notes for review: package slugs map directly to the CENTRAL_AGENTIC_OPS_<PACKAGE>_MODE/_MAX_REPOS variables used by the workflows, and the catalog ref is pinned to main in the prompt — worth deciding whether it should point at a release tag instead.